Systems and methods for managing and making patent annuity payments

ABSTRACT

Various embodiments of the present disclosure include systems and methods of making or managing annuity payments. In one example embodiment, a method comprises tracking one or more patent annuity payments due on at least one patent for a user and docketing a due date for at least one of the annuity payments. In advance of the due date, the method includes identifying the cost of a forward contract to obtain or purchase currency equal to a total amount payable of the at least one annuity payment and providing the cost of the forward contract to the user.

RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. 119(e) of U.S. Provisional Patent Application Ser. No. 61/542,515 filed Oct. 3, 2011, which is incorporated herein by reference in its entirety and made a part hereof. This application also claims the benefit under 35 U.S.C. 119(e) of U.S. Provisional Patent Application Ser. No. 61/561,502 filed Nov. 18, 2011, which is incorporated herein by reference in its entirety and made a part hereof.

BACKGROUND

The management of a patent portfolio involves multiple stages. Initially, a decision is typically made as to which inventions are worth the investment of filing a patent application. Each filed patent application typically then goes through prosecution with the patent office. Finally, for each patent that is allowed, maintenance fees are usually payable at a variety of intervals to keep the patent in force.

It is well known that annuity payment providers can make large sums on currency conversion. That is, they typically convert for example dollars to euros for example when paying a European Patent Office (EPO) annuity fee, and charge more than the commercial exchange rate—typically 6 to 25 percent more than going rate. This markup is typically justified by the provider as compensation for volatility in currency markets. In the eyes of a patent manager, for example, the markup can unduly add to the maintenance costs of a patent estate.

The inventor has recognized that one solution to this problem can include a payment infrastructure that can support a more economical way to price and convert currency using forward contracts. Generally, the price of a forward contract is the cost of the currency on the day the contract is purchased, plus the cost of interest to hold the currency until it is delivered. This could be as little as 1% in interest cost, as compared to a 6% to 25% mark up. Other components of the contract cost or price can include currency conversion charges, or bank service charges.

SUMMARY

This disclosure relates to systems and methods for making or managing patent annuity payments.

In an example embodiment, an annuity payment management system comprises at least one hardware-implemented module including at least one processor to track one or more patent annuity payments due on at least one patent for a user; docket a due date for at least one of the annuity payments; in advance of the due date, identify the cost of a forward contract to obtain or purchase currency equal to a total amount payable on the at least one annuity payment; and provide the cost of the forward contract to the user.

The at least one processor may be further to receive, in response to providing the cost of the forward contract, annuity payment instructions from the user. The at least one processor may be further to pay, or arrange to have paid, at least one annuity payment based on the received instructions. The at least one annuity payment may be due on a foreign patent and the currency may be a foreign currency. The due date of the at least one annuity payment may fall within a specified period, and the cost identification may occur on a date in advance of the specified period.

The at least one processor may be further to receive data identifying one or both of the specified period and the cost identification date from the user. The at least one processor may be further to apportion at least one component of the cost of the forward contract across a plurality of tracked annuity payments. The component may be one or more of an interest charge, a currency conversion charge, and a bank or service charge relating to at least one aspect of the forward contract. The apportionment may be performed pro-rata based on a base cost of each annuity payment.

In an example embodiment, an annuity payment management system comprises at least one hardware-implemented module including at least one processor to allow a user to register with the system and to identify at least one patent on which an annuity is payable; generate, synchronize or receive annuity tracking data relating to the at least one patent, the tracking data including a due date of the annuity payment; identify, in a first currency, the amount payable on the annuity payment; price, in advance of the due date and using forward contract rates from a participating bank, a forward contract for obtaining currency to have the annuity payment paid in a second currency; and provide the contract pricing to the user or a third party.

The at least one processor may be further to receive, in response to providing the contract pricing, annuity payment instructions from the user or the third party. The at least one processor may be further to pay, or facilitate payment of, the annuity payment based on the received instructions.

In an example embodiment, the at least one processor may be further to facilitate receipt, from the user or the third party and in the first currency, funds at least including the amount payable on the annuity payment; and pay, or facilitate payment of, the annuity payment in the second currency.

The tracking data may include data received from a third party annuity service, or a patent office.

The annuity payment may be included in a batch of annuity payments due in a specified period, and the forward contract may include at least a total amount due for all the annuity payments in the batch. At least a portion of an interest or service charge included in the forward contract may be apportioned across the batch of annuity payments. The apportionment may be performed pro-rata based on a base cost of each annuity payment in the batch.

In an example embodiment, the third party may be an annuity payment service provider. The at least one processor may be further to dynamically quote the contract pricing to the user or third party in advance of the due date.

In an example embodiment, an annuity payment management system comprises a network; at least one database, accessible on the network, the database including data relating to annuity payments due on patents or applications registered at a patent office; a server, operatively connected to the network, wherein the server includes a processor, a memory, software operable on the processor to track one or more patent annuity payments due on at least one patent in the database; docket a due date for at least one of the annuity payments; in advance of the due date, identify the cost of a forward contract to obtain or purchase currency equal to a total amount payable on the at least one annuity payment; and provide the cost of the forward contract to a user.

In an example embodiment, an annuity payment management system comprises a network; at least one database, accessible on the network, the database including data relating to annuity payments due on patents or applications registered at a patent office; a server, operatively connected to the network, wherein the server includes a processor, a memory, software operable on the processor to allow a user to register with the system and to identify at least one patent on which an annuity is payable. Further, an annuity payment management system may generate, synchronize or receive annuity tracking data relating to the at least one patent, the tracking data including a due date of the annuity payment; identify, in a first currency, the amount payable on the annuity payment; price, in advance of the due date and using forward contract rates for obtaining currency to have the annuity payment paid in a second currency; and provide the contract pricing to the user or a third party.

BRIEF DESCRIPTION OF DRAWINGS

Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:

FIG. 1 is a schematic view of a computer network system, according to various embodiments.

FIG. 2 is a user interface, as may be used in an example embodiment.

FIG. 3 is a block diagram of a system, according to example embodiments.

FIGS. 4A-4B are flow charts showing methods, according to example method embodiments.

FIG. 5 is a block diagram of a machine in the example form of a computer system within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies herein discussed.

DETAILED DESCRIPTION

The life cycle of a patent may include multiple stages. These stages generally include invention, filing a patent application on the invention, prosecuting the patenting application to allowance or abandonment, determining whether to file any continuing applications, and paying maintenance fees on the allowed patent.

At each stage, one or more parties determine the best course of action to take with respect to the invention. For example, when determining whether or not to file a patent, the inventor may know what products are out in the technology area of the invention, a business manager may know how the invention fits in with a company's goals, and a patent attorney may have researched existing patents or applications in the technology area of the patent. These parties will ultimately decide whether it is worth the initial investment of filing an application on the invention and then determine the next course of action at each future stage.

In some instances, an inventor, business manager, or portfolio manager may wish to monitor the patent activities of one or more competitors. The provision of up-to-date information relating to cited references or technology trends in the art to which a user's or competitor's patent portfolio relates may be particularly helpful in devising patenting strategy or making informed business decisions.

In various embodiments, a patent management system includes tools to help the parties involved in the patenting process make decisions at each stage in the life of a patent. These tools may also be used for general research by parties not immediately involved with the patenting of the invention. These tools may be used as standalone tools, in combination with other tools, and in combination with other patent management systems. Examples of tools include, but are not limited to, prosecution analytics, patent and patent continuation analysis, reference management, prior art analytics, docketing management, claim mapping, claim analytics, portfolio analytics, external database (e.g., Patent Application Information Retrieval “PAIR”) analytics, annuity management, strategic monitoring, and a white space indicator.

The systems, methods, and tools of the present disclosure set forth in this specification are described in relation to a patent management system and patent matters, but it will be understood that embodiments of the present invention could equally be applied to other forms of intellectual property (trademarks, copyright, utility models, petty patents, registered designs, and the like). Moreover, the term “patent” is not intended to be limited to an issued patent, but may include a pending patent application or un-filed application, invention disclosure or other type of intellectual property right. The term “user” or “registered user” is intended to cover any person interacting with the patent management system. A user may be an inventor, portfolio manager, business manager or patent attorney, for example. A “user” or “registered user” may also be an annuity payment service provider such as Computer Packages, Inc (CPI) or Computer Patent Annuities (CPA), for example. In the patent art, the term “annuity fees” can sometimes be used to refer to payments required to renew granted patents, while the term “maintenance fees” can sometimes be used to refer to payments required to maintain pending patent applications. In this specification, the terms “annuity fees” and “maintenance fees” are used interchangeably and refer to any kind of payment required to keep a patent or patent application (or other intellectual property right) in force.

FIG. 1 is a schematic view of computer network system 100 according to various embodiments. The computer network system 100 includes a patent portfolio and annuity management system 102 (also called a portfolio management system 102, or annuity management system 102) and user terminal 104, communicatively coupled via network 106. In an embodiment, patent portfolio and annuity management system 102 includes web server 108, application server 110, database management server 114, which is used to manage at least operations database 116, and file server 118. Patent portfolio and annuity management system 102 may be implemented as a distributed system; for example, one or more elements of the patent portfolio and annuity management system 102 may be located across a wide area network (WAN) from other elements of patent portfolio and annuity management system 102. As another example, a server (e.g., web server 108, file server 118, database management server 114) may represent a group of two or more servers, cooperating with each other, provided by way of a pooled, distributed, or redundant computing model.

Network 106 may include local area networks (LANs), WANs, wireless networks (e.g., 802.11 or cellular network), the Public Switched Telephone Network (PSTNs) network, ad hoc networks, personal area networks (e.g., Bluetooth) or other combinations or permutations of network protocols and network types. The network 106 may include a single LAN or WAN, or combinations of LANs or WANs, such as the Internet. The various devices coupled to network 106 may be coupled to network 106 via one or more wired or wireless connections.

Web server 108 may communicate with file server 118 to publish or serve files stored on file server 118. Web server 108 may also communicate or interface with the application server 110 to enable web-based presentation of information. For example, application server 110 may provide scripts, applications, or library files that provide primary or auxiliary functionality to web server 108 (e.g., multimedia, file transfer, or dynamic interface functions). In addition, application server 110 may also provide some or the entire interface for web server 108 to communicate with one or more of the other servers in the patent portfolio and annuity management system 102 (e.g., database management server 114). Web server 108, either alone or in conjunction with one or more other computers in patent portfolio and annuity management system 102, may provide a user-interface. The user-interface may be implemented using a variety of programming languages or programming methods, such as HTML (HyperText Markup Language), VBScript (Visual Basic® Scripting Edition), JavaScript™, XML® (Extensible Markup Language), XSLT™ (Extensible Stylesheet Language Transformations), AJAX (Asynchronous JavaScript and XML), Java™, JFC (Java™ Foundation Classes), and Swing (an Application Programming Interface for Java™)

User terminal 104 may be a personal computer (PC) or mobile device. In an embodiment, user terminal 104 includes a client program to interface with the patent portfolio and annuity management system 102. The client program may include commercial software, custom software, open source software, freeware, shareware, or other types of software packages. In an embodiment, the client program includes a thin client designed to provide query and data manipulation tools for a user of user terminal 104. The client program may interact with a server program hosted by, for example, application server 110. Additionally, the client program may interface with database management server 114.

Operations database 116 may be composed of one or more logical or physical databases. For example, operations database 116 may be viewed as a system of databases, which when viewed as a compilation, represent an “operations database.” Sub-databases in such a configuration may include a matter database, portfolio database, user database, patent reference document or prior art database, product database, watch database, and mapping database. The operations database 116 or any one of the sub-databases may include a registry of patent matters. Operations database 116 may be implemented as a relational database, a centralized database, a distributed database, an object-oriented database, or a flat database in various embodiments.

Data stored in a first database may be associated with data in a second database through the use of common data fields. For example, consider entries in the patent database formatted as [Patent ID, Patent Number] and entries in the product database formatted as [Product ID, Product Name, Patent ID]. In this manner, a product entry in the product database is associated with a patent in the patent database through the Patent ID data field. In various embodiments, a product may be associated with more than one patent by creating multiple entries in the product database (e.g., one for each patent the product is associated with). In other embodiments, one or more patent reference document may be associated with a patent by creating multiple entries in the patent database, for example. The formats and data field titles are for illustration purposes, and other names and formats may be used. Additionally, further associations between data stored in the databases may be created as discussed further herein.

During operation of patent portfolio and annuity management system 102, data from multiple data sources (internal and external) is imported into or accessed by the operations database 116. Internal sources may include data from portfolio management and annuity payment services affiliated with patent portfolio and annuity management system 102. External sources 120 may include websites or databases associated with foreign and domestic patent offices (e.g., PAIR at the United States Patent and Trademark Office “USPTO”), assignment databases, World Intellectual Property Organization (“WIPO”), and International Patent Documentation Center (“INPADOC”). In an embodiment, annuity amounts due and annuity due dates for patent matters listed in a registry database are drawn directly from such data stored at a national patent office in electronic form. In various embodiments, the data is scraped and parsed from websites if it is unavailable through a database. The data may be gathered using API calls to the sources when available. The data may be imported and stored in the operations database 116 on a scheduled basis, such as weekly, monthly, quarterly, or some other regular or periodic interval. Alternatively, the data may be imported on-demand.

After data importation, the data may be standardized into a common format. For example, database records from internal or external sources 120 may not be in a compatible format with the operations database 116. Data conditioning may include data rearrangement, normalization, filtering (e.g., removing duplicates), sorting, binning, or other operations to transform the data into a common format (e.g., using similar date formats and name formats).

FIG. 2 is an example user interface 200 of patent portfolio and annuity management system 102 (FIG. 1). User interface 200 is illustrated with multiple user interface elements. In an example embodiment, a user interface element is a graphical or textual element with which a user may interact to cause an application to perform an assigned action for the interface element. Data representing user interface 200 may be transmitted via network 106 and presented on a display of user terminal 104 (FIG. 1) through the use of a web browser. A user (e.g., manager of a patent portfolio) may interact with the user interface elements of user interface 200 through the use of an input device (e.g., stylus, cursor, mouse, finger) of the user terminal 104. In an embodiment, a user selection is based on the coordinates of the input device as it makes contact with the display or where a user “clicks” the mouse. The coordinates are compared to the coordinates of the user input element to determine the selection. The type of user elements, names, and layout depicted in FIG. 2 are intended to be an illustration of an example user interface of patent portfolio and annuity management system 102. Other types of user elements, names, and layouts may be used.

The user interface elements may include my matters 202, patent watches 204, company watches 206, patent analysis 207, and tag matters 209. These elements may be used to select a context/view of the portfolio and annuity management system 102 (FIG. 1). For example, my matters 202 may list the patents included within a portfolio of a user, or list patent matters tagged for renewal by a user of an annuity registry database included, for example, in an operations database 116 (FIG. 1) of the type described above. Patent watches 204 may list information on patents that the user has indicated the management system 102 is to watch, and company watches 206 lists information on companies that the user has indicated the annuity management system should watch. Patent analysis 207 may allow a user to perform analysis on selected patent or patent continuation matters. Tag matters 209 may be selected to allow a user to tag or identify patent matters for management or payment of annuity fees. Further details of each of these are included herein.

Date boxes 208 and 210 are user elements that allow a user to select a time period, for example to select a display of patents having annuity fees due in that time period. Amount due box 212 displays the amount due with respect to annuities for patents in the portfolio of the user, or tagged or listed in a registry, within the period indicated by date boxes 208 and 210. Upon activating (e.g., clicking) one of the date boxes 208 and 210, a user may be presented with a calendar, which allows the selection of a date. Upon selecting a date, the date boxes 208 and 210 will update to reflect the user's choice.

Drop-down menu 214 includes a list of portfolios or registry listings that a user of the patent portfolio and annuity management system 102 (FIG. 1) is authorized to view. For example, before user interface 200 is displayed, a login screen requesting a user ID and password may be presented to the user. In various embodiments, the user ID is associated with one or more portfolios. In turn, each portfolio is associated with one or more matters. Matters may include US and foreign issued patents (including divisionals, continuations and so forth), pending patents, abandoned patents, and not yet filed applications. Thus, upon selection of a portfolio using drop-down menu 214, user interface 200 is populated with matters associated with the portfolio or registry listing.

Checkbox 216 is an option to only display matters that currently have an annuity due. Drop-down menu 218 allows further filtering of matters. For example, the matters may be filtered by US patents only, by US patent applications, and by foreign applications only.

In various embodiments, activation of button 220 updates user interface 200 to reflect the choices made by the user with respect to date boxes 208 and 210, checkbox 216, and drop-down menu 218. For example, the amount due box 212 will be updated to reflect the amount due within the new period, and the matters listed under column headings 222 may be filtered. In various embodiments, user interface 200 is updated as the user selections are made with respect to elements 208 to 218 without activating button 220.

FIG. 3 is a block diagram of patent portfolio and annuity management system 102 (FIG. 1), according to an example embodiment. Illustrated are user database 302, portfolio database 304, matter database 306, watch database 308, product database 310, analytics database 312, input module 314, parsing module 316, analytics module 318, display module 320, filtering module 322, mapping module 324, and payment module 326. In various embodiments, the data stored in databases 302, 304, 306, 308, 310, and 312 may be in the same or multiple physical locations. For example, portfolio database 304 may be located in one or more computers associated with a portfolio management service. In various embodiments, patent portfolio and annuity management system 102 (FIG. 1) may mirror databases stored in other locations. In an embodiment, when a request is made to access data stored in the databases, patent portfolio and annuity management system 102 determines where the data is located and directs the request to the appropriate location.

In an example embodiment, user database 302 stores data representing users of patent portfolio and annuity management system 102 (FIG. 1). The data may represent authorized or registered users that are registered to use the patent matter registry database, for example. The data may include data fields of user credentials, including a user ID and password, and access rights with respect to the management system 102. The user ID may be the same as the user ID of other systems associated with patent portfolio and annuity management system 102. For example the user ID may be used in a portfolio management system 102. In this manner, access rights of the user with respect to the portfolio management part of the system 102 may follow to the annuity management part of the system. In various embodiments, each user ID is associated with one or more portfolio IDs. Thus, when a user logs into the patent portfolio and annuity management system 102, the user is presented with access to only the portfolios that have been associated with that user ID. More or fewer data fields associated with a user may be included in a user entry stored in user database 302.

Portfolio database 304, in an example embodiment, stores data representing portfolios of one or more matters. A matter may include foreign or domestic issued patents in addition to applications. Data stored in portfolio database 304 may have been initially generated in a portfolio management system and imported into patent portfolio and annuity management system 102 through the use of one or more API calls or direct access to the data in the portfolio management system 102. In various embodiments, a portfolio may be generated by a user using the patent portfolio and annuity management system 102. For example, a user interface may be presented to the user requesting a portfolio name and the identifiers of matters to be included in the portfolio. In an embodiment, a portfolio entry in portfolio database 304 includes the data fields of portfolio ID and portfolio name. Additionally, a data field for matter ID may also be included in an entry in the portfolio database 304. Thus, each portfolio may be associated with one or more matters through the use of the matter ID data field. More or fewer data fields associated with a portfolio may be included in a portfolio entry of portfolio database 304.

In an embodiment, matter database 306 stores data representing matters. Each matter may be associated with one or more portfolios as well as one or more watches. In some embodiments, a matter is associated with no portfolios or watches. In an embodiment, a matter entry includes data fields representing a matter ID, title (e.g., the name of the patent or application), type of the matter (e.g., application, issued patent, Patent Cooperation Treaty “PCT” application), status of the matter (e.g., issued, abandoned, allowed), a link to the patent office where the matter was filed, a link to a PDF download of the matter, abstract of the matter, inventors of the matter, current owner of the matter, cited references on the face of the matter, filed date, issue date, docket number, and annuity information (e.g., due date, country, and amount due). In some embodiments, other patent reference documents or prior art in any form may be stored and associated with one or more matters. More or fewer data fields associated with a patent may be included in a matter entry stored in matter database 306. In an example embodiment, matter database 306 may store a patent matter database, wherein this database includes data about the patent matters. The data may include, for at least one patent matter, a claim set or statement of invention and a priority date for the claim set or statement of invention. Matter database 306 may also store a database of prior art documents (also known as “references”), wherein the prior art database includes data about the prior art documents. The data may include, for at least one prior art document, a priority date or publication date of the document. One or more of the prior art documents may be associated with a first patent matter in the patent matter database.

In various embodiments, a matter is associated with one or more other matters as a family with a family ID. Family members may be priority documents, continuation patents/applications, divisional patents/applications, and foreign patent/application counterparts. In an embodiment, family information is determined according to an external source such as INPADOC. Patent reference documents and/or other prior art may be manually or automatically stored, cross-cited, and associated with related family matters, for example.

In an embodiment, watch database 308 stores data representing user preferences with respect to objects that the user wants to track (e.g., watch). In an embodiment, an object is a company or a matter. With respect to matters, a user may indicate a preference to track the matter for any forward citations within a time period (e.g., 60 days, 3 months, etc.). Thus, watch database 308 may store entries with a watch ID that is associated with a user ID and a matter ID. With respect to companies, a user may indicate a preference to watch for publications or issued patents with an associated time period. Thus, watch database 308 may store entries with a watch ID, a user ID, and a company name. In various embodiments, the watches are user ID-specific such that no matter which profile the user is viewing, the watches do not change.

In an embodiment, product database 310 stores data representing products. The products may be actual products manufactured by the user, products yet to be released, planned products, products covered in a licensing agreement, or a fictional product. In various embodiments, product database 310 stores entries with a product ID and product name which are associated with a user ID. In various embodiments, a user may tag a product as associated with a matter. Thus, an entry in the product database 310 may also be associated with a matter ID. In an embodiment, one or more products stored in the product database 310 may be mapped to one or more matters stored in the matter database 306.

In various embodiments, analytics database 312 stores data representing information on matters and companies associated with patent portfolio and annuity management system 102 (FIG. 1). This information may be organized according to an individual matter, a portfolio, a family, or company. The information may be gathered from internal or external sources 120 of patent portfolio and annuity management system 102 or may be generated by examining the data stored in one or more databases of the management system 102.

In various embodiments, information for an individual matter may include status (e.g., disclosure received, drafting, filed, completed-waiting examination, in prosecution, allowed, issued), cited prior art, list and type of rejections (e.g., 35 U.S.C.§101, 102, 103), number of claims allowed, office action count, interviews held, Information Disclosure Statements (“IDS's”) filed, attorney fees to date, and PTO fees to date. Further metrics for an individual matter stored in analytics database 312 may include time waiting for examiner, total time in examination, time waiting for PTO while in examination, and time on appeal. An additional prosecution details formatter may include upcoming docket dates (e.g., due dates for office action, IDS due dates, etc.). A claim prosecution history chart may also be stored in analytics database 312 for each matter. The prosecution history may include a history of claim amendments and arguments made in prosecution.

In various embodiments, analytics for an individual matter may also include data representing a claim chart. The claim chart may include one or more scope concepts on one axis and claims on the other axis. In an embodiment, a scope concept is a textual description of what a patent claim is at least limited to. Thus, if a claim comprises A, B, and C, a scope concept may be A. In various embodiments, a scope concept for the claim may be broader than A because the claim will still be limited to the broader scope concept. In an embodiment, the claim charts store mappings between claims and scope concepts. The claim chart may include a variety of levels of granularity of scope concepts. Some claims may be mapped to all of the scope concepts while others may not be mapped to any scope concepts. In various embodiments, the mappings may have already been generated in a program external to the management system 102 (FIG. 1) (e.g., a portfolio mapping system). In various embodiments, claim charts may be combined at the portfolio level. Thus, a portfolio level chart may include scope concepts for all the claims (or, in some examples, only the independent claims) in the portfolio.

In various embodiments, portfolio and family analytics information may be stored in analytics database 312 based on aggregating the metrics for an individual matter. In an embodiment, the analytics of a family may differ from those in a portfolio since not all family member matters may be part of a portfolio. Additionally, the analytics may be stored for multiple time periods such that comparisons may be made between current metrics and metrics from a year ago (or other time period).

Aggregated metrics may include total patents and applications, pending and waiting for examination, in prosecution with no claims allowed, in prosecution with some claims allowed, appealed, notice of allowance received, and issued. These metrics may be compiled for both US and international matters in the portfolio. Additional information may include the international portfolio distribution by country. An age distribution of the portfolio may also be compiled. For example, the portfolio may be broken down by less than one year old, 1 to 3 years old, 3 to 5 years old, 5 to 10 years old, 10 to 20 years old, and 20 or more years old. Recent filing and issue activity as well as upcoming foreign filing deadlines may be stored in analytics database 312.

In various embodiments, prosecution metrics across a portfolio or family are determined and stored in analytics database 312. This data may include matters waiting for examination, matters in examination, matters appealed, and cases allowed but not yet issued. Analytics with respect to office actions may also be compiled and stored. For example, success of allowance after a first office action response, a second response, and the like, may be stored in analytics database 312. Additional prosecution analytics may include allowance rate (e.g., 10%) after a telephone interview, allowance after an in-person interview, percentage of interviews with response, number and type of rejections, average time in prosecution (e.g., in months), average time to file a response, and average time to next office action. Further, the list of recently allowed cases, recently appealed cases, stalled cases, and recently abandoned cases may also be stored for each portfolio and family in analytics database 312.

In various embodiments, data stored in the database 312 for a group of matters in a portfolio or family is analyzed to determine the top (e.g., ten) most cited patents, top most cited inventors, top most cited prior art owners (e.g., according to assignment documents or the face of the patent), newly (e.g., within the last 60 days) cited prior art owners, and top most cited prior art inventors. This information may be stored in analytics database 312.

In various embodiments, annuity cost information regarding cost projections for both US issued patents and international patents may also be stored. Upcoming foreign filing deadlines with respect to annuities may also be stored in analytics database 312.

In various embodiments, the results of keyword analysis on one or more matters and/or prior art references may be stored in analytics database 312. The keyword analysis may be based on the occurrences of the keywords in the matter or references to derive a score or keyword overlap.

In various embodiments, input module 314 receives data from multiple sources where it may be further processed by one or more other modules and stored in one or more of databases 302-312. For example, input module 314 may be configured to utilize one or more APIs to collect data from one or more external sources 120 (FIG. 1) (e.g., public PAIR, private PAIR, INPADOC, foreign patent offices, patent docketing systems, portfolio management systems, etc.). The data may include published patent documents (for example, published claims of a patent), issued patent documents (for example, granted claims of a patent), patent applications, office actions or other patent office correspondence, prior art references, claim mappings, dockets dates, and annuity payment data.

In various embodiments, input module 314 is configured to receive input from one or more user interface elements. For example, the patent portfolio and annuity management system 102 (FIG. 1) may present multiple user interfaces to users. These user interfaces may enable users to input data directly into databases 302-312, instruct the management system 102 to retrieve data from patent data stores, and instruct the management system 102 to perform various operations on the data in databases 302-312.

Additionally, input module 314 may be configured to determine the selection of one or more user interface elements by a user and initiate the action associated with the selected user interface element. For example, a user interface element may include a drop-down menu to select a portfolio. Input module 314 may be configured to receive a selection of the portfolio and a drop-down menu. Then, input module 314 may pass the selection to one or more other modules for further processing. For example, display module 320 may update the drop-down menu to indicate the selection of a portfolio.

In various embodiments, parsing module 316 takes the data that has initially been inputted by input module 314 and formats it according to the data fields of databases 302-312 as discussed above. For example, consider a patent publication that has been inputted by input module 314. Parsing module 316 may use a combination of automatic image recognition and text analysis to determine the filing date, issue date, title, abstract, and claims of the patent. In some embodiments, parsing module 316 may flag certain pieces of data that had been determined to be potentially inaccurate (e.g., a number that could not be read). A user of patent portfolio and annuity management system 102 may then examine the flagged data and manually enter in the information.

The resulting data that has been parsed by parsing module 316 may then be entered as an entry in one or more of databases 302-312. This may be accomplished by, for example, formulating an SQL query with the parsed information. In various embodiments, parsing module 316 may parse multiple pieces of information before generating a database entry. For example, input module 314 may receive a docket number for an issued patent. The docket number may be combined with the information parsed from the issued patent to form an entry in matter database 306.

In various embodiments, analytics module 318 is configured to examine and run calculations on the data stored in the databases 302-312 to generate the analytics discussed previously. For example, analytics module 318 may formulate an SQL query that retrieves the number of times that a prior art reference has been cited within a portfolio. This query may be run for each prior art cited within the portfolio to determine a list of the most cited (e.g., the top ten) prior art references within a portfolio. In an embodiment, the queries are formulated and run as requested by a user. In an embodiment, once the analytics information has been determined, it is stored within analytics database 312. In various embodiments, queries are formulated and run on a periodic basis (e.g., nightly) and entries in analytics database 312 may be updated to reflect any changes.

In an embodiment, display module 320 is configured to display user interfaces and information retrieved from one or more databases 302-312. For example, display module 320 may generate user interface 200 of FIG. 2. If a user is accessing patent portfolio and annuity management system 102 (FIG. 1) remotely (e.g., through a web browser), display module 320 may be configured to transmit data representing a user interface through a network to a user terminal 104 (FIG. 1). In various embodiments, display module 320 is configured to generate one or more charts of data stored in databases 302-312. For example, display module 320 may generate a pie chart of the top 10 inventors within a portfolio.

In various embodiments, filtering module 322 is configured to filter a set of matters according to a user preference. For example, a user may activate a check box that indicates only pending matters should be shown in a user interface. Filtering module 322 may formulate a query consistent with retrieving only pending matters. The results of the query may then be shared with display module 320, where the user interface may be updated.

In various embodiments, mapping module 324 is configured to receive or generate mappings from a product to a matter. This may be accomplished, for example, by receiving a selection of a product and a matter by the user. The product may be one or more of the products stored in product database 310. In various embodiments, mapping module 324 is configured to present an automated mapping of the product to a matter for the user to confirm or deny. For example, mapping module 324 may present a claim chart for an issued patent to a user. As discussed, the claim chart includes one or more scope concepts to which one or more the claims of the patent are limited. In conjunction with input module 314, mapping module 324 may receive selections of the user of one or more of the scope concepts that are potentially affiliated with the product. Thus, a comparison may be made between what the claims are limited to and what the product may be. For example, if a product, as defined by the selection of one or more scope concepts by the user, is affiliated toward scope concepts A, B, and C, and claim 1 of the patent has been mapped to scope concepts A, B, and C, the mapping module 324 may present an option to map the product to the patent. In various embodiments, the user may override this recommendation and select to not map the product to the patent. Similarly, a user may indicate that a product is affiliated with the patent even if the scope concepts do not match.

In various embodiments, the mapping module 324 is configured to receive or generate mappings from prior art to a matter. This may be accomplished, for example, by receiving a selection of prior art and a matter by the user. The selection of the prior art may be based on cited references or through other external prior art search. The selections may be conducted manually, by a user, or automatically, by analytics module 318, for example. In various embodiments, mapping module 324 is configured to present an automated mapping of the prior art to a matter for the user to review. In various embodiments, the mapping module 324 can be configured to carry out any of the keyword analysis described above in relation to analytics module 318, or to map products stored in product database 310.

In an embodiment, once the product or prior art mapping information has been determined, it is stored within analytics database 312 or matter database 306. In various embodiments, queries are formulated and run on a periodic basis (e.g., nightly), and entries in analytics database 312 or matter database 306 may be updated to reflect any changes.

In one example embodiment, an annuity system or service tracks annuity payments due for a patent owner (like a large US or European company “EC”, for example) listing payments in US dollars. The system has software that dockets a due date for each patent to generate tracking data. At a specified date in advance of the due date, for example 3 or 6 months, the software prices out how much it would cost to buy a forward contract of currency equal to the total amount of fees due on all patents being tracked that are coming due on that particular date, or due within a date range, like all fees due in a calendar month. In an alternate embodiment, this can be done for one patent at a time. The cost of the forward contract is then apportioned to all the patents pro-rata based on the actual annuity fee, for the purpose of showing how much it will cost to pay each maintenance fee. The system provides the pricing infrastructure to support this transaction. The pricing infrastructure and functionality may be included in one or more of the modules described herein, for example the analytics module 318 or the payment module 326 described further below.

In an example method embodiment, a patent owner (EC) signs up to use the annuity service. The service generates, synchronizes or receives the tracking data. In an example embodiment, the tracking data is received from the EC's existing annuity payment service, for example Computer Patent Annuities (CPA). On a specified day in advance of when a batch of annuity payments are due in a foreign patent office (the EPO, for example), the service prices a forward contract for that batch of patent annuities using forward contract rates from a participating bank. The price of the currency may be provided to the patent owner directly, or provided to an annuity payment company (APC), which in turn uses the information to send upcoming payment reports to the patent owner with, for example, a list of annuities due and an amount for each payment. The patent owner can instruct the APC to make payments in US dollars. The APC may notify the service or the participating bank on how much to send to the foreign patent office to cover the cost of payment for the list of annuities to be paid. The participating bank may wire or transfer funds to a foreign patent office account. In an example embodiment, this step (or any of the other steps) may be automated.

In an example embodiment, the patent owner (EC) may pay the participating bank directly for the cost of the annuities. In another embodiment, the APC pays the participating bank and the APC collects from the patent owner or the existing annuity service (CPA for example). The method can be replicated to pay fees in any country.

In an example embodiment of the system or service, a user could either have a default forward date or pick a specific date dynamically as the forward date. In an example embodiment, a user interface is integrated into a patent office payment system. In an example embodiment, the pricing for one or more annuity payments is dynamically quoted during the payment authorization process. The price may be locked with the order to pay the one or more annuities. A credit card or account of the patent owner may be charged later than the annuity due date or a date before that.

In various embodiments, payment module 326 is configured to receive selections, or tags, by the user of which annuities to pay for matters in a portfolio or registry listing, for example. Additionally, payment module 326 may receive user preferences related to the payment of the annuities. Payment module 326 may receive payment information from a user and forward the payment information to the appropriate agency/office. In some embodiments, the annuity management system 102 (FIG. 1) organizes payment of the annuity on behalf of the user, and the user pays patent portfolio and annuity management system 102.

Any of the databases 302-312 or modules 314-326 described above may be used or configured partially or entirely as appropriate to perform one or more of the annuity payment or management functions described herein, or as set forth below in the following method steps.

Some embodiments of the present inventive subject matter include methods for making or managing annuity payments. One such embodiment is illustrated in FIG. 4A. In this example embodiment, a method 400 comprises: at 402, tracking one or more patent annuity payments due on at least one patent for a user; at 404, docketing a due date for at least one of the annuity payments; at 406, in advance of the due date, identifying the cost of a forward contract to obtain or purchase currency equal to a total amount payable of the at least one annuity payment; and at 408, providing the cost of the forward contract to the user.

In an example embodiment, the method 400 further comprises receiving, in response to providing the cost of the forward contract, annuity payment instructions from the user. The method 400 may further comprise paying, or arranging to have paid, at least one annuity payment based on the received instructions. The at least one annuity payment may be due on a foreign patent and the currency may be a foreign currency. The due date of the at least one annuity payment may fall within a specified period, and the cost identification may occur on a date in advance of the specified period.

In an example embodiment, the method 400 further comprises receiving data identifying one or both of the specified period and the cost identification date from the user.

In an example embodiment, the method 400 further comprises apportioning at least one component of the cost of the forward contract across a plurality of tracked annuity payments. The component may be one or more of an interest charge, a currency conversion charge, and a bank or service charge relating to at least one aspect of the forward contract. The apportionment may be performed pro-rata based on a base cost of each annuity payment in the plurality of annuity payments.

Another method embodiment is illustrated in FIG. 4B. In this example embodiment, a method 410 comprises; at 412, allowing a user to register with the service and to identify at least one patent on which an annuity is payable; at 414, generating, synchronizing or receiving annuity tracking data relating to the at least one patent, the tracking data including a due date of the annuity payment, and identifying, in a first currency, the amount payable on the annuity payment; at 416, pricing, in advance of the due date and using forward contract rates from a participating bank, a forward contract for obtaining currency to have the annuity payment paid in a second currency; and at 418, providing the contract pricing to the user or a third party.

In an example embodiment, the method 410 further comprises receiving, in response to providing the contract pricing, annuity payment instructions from the user or the third party. The method 410 may further comprise paying, or arranging to have paid, the annuity payment based on the received instructions. The method 410 may yet further comprise receiving, from the user or the third party and in the first currency, funds at least including the amount payable on the annuity payment; and paying, or arranging to have paid, the annuity payment in the second currency. The tracking data may include data received from a third party annuity service, or a patent office.

In an example embodiment, the annuity payment is included in a batch of annuity payments due in a specified period, and the forward contract may include at least a total amount due for all the annuity payments in the batch. At least a portion of an interest or service charge included in the forward contract may be apportioned across the batch of annuity payments. The apportionment may be performed pro-rata based on a base cost of each annuity payment in the batch. The third party may be an annuity payment service provider. In an example embodiment, the pricing of the forward contract is dynamically quoted to the user or third party in advance of the due date.

Any of the example methods may be computer-implemented and any one or more of the above-cited method steps including tracking, docketing, identifying and providing may be performed by at least one processor. The at least one processor may be included in one or more modules, including hardware-implemented modules of the type described herein.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied (1) on a non-transitory machine-readable medium or (2) in a transmission signal) or hardware-implemented modules. A hardware-implemented module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client, or server computer system) or one or more processors may be configured by software (e.g., an application or application portion) as a hardware-implemented module that operates to perform certain operations as described herein.

In various embodiments, a hardware-implemented module may be implemented mechanically or electronically. For example, a hardware-implemented module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware-implemented module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware-implemented module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

Accordingly, the term “hardware-implemented module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily or transitorily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein. Considering embodiments in which hardware-implemented modules are temporarily configured (e.g., programmed), each of the hardware-implemented modules need not be configured or instantiated at any one instance in time. For example, where the hardware-implemented modules comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different hardware-implemented modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware-implemented module at one instance of time and to constitute a different hardware-implemented module at a different instance of time.

Hardware-implemented modules can provide information to, and receive information from, other hardware-implemented modules. Accordingly, the described hardware-implemented modules may be regarded as being communicatively coupled. Where multiple of such hardware-implemented modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware-implemented modules. In embodiments in which multiple hardware-implemented modules are configured or instantiated at different times, communications between such hardware-implemented modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware-implemented modules have access. For example, one hardware-implemented module may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware-implemented module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware-implemented modules may also initiate communications with input or output devices and can operate on a resource (e.g., a collection of information).

The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules.

Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment, or as a server farm), while in other embodiments the processors may be distributed across a number of locations.

The one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., APIs).

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry, or in computer hardware, firmware, or software, or in combinations of them. Example embodiments may be implemented using a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.

A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

In example embodiments, operations may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method operations can also be performed by, and apparatus of example embodiments may be implemented as, special purpose logic circuitry (e.g., a FPGA or an ASIC).

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In embodiments deploying a programmable computing system, it will be appreciated that both hardware and software architectures usually require consideration. Specifically, it will be appreciated that the choice of whether to implement certain functionality in permanently configured hardware (e.g., an ASIC), in temporarily configured hardware (e.g., a combination of software and a programmable processor), or a combination of permanently and temporarily configured hardware may be a design choice. Below are set out hardware (e.g., machine) and software architectures that may be deployed in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 5 is a block diagram of a machine in the example form of a computer system 500 within which instructions for causing the machine to perform any one or more of the methodologies discussed herein may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a PDA, a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system 500 includes a processor 502 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 504 and a static memory 506, which communicate with each other via a bus 508. The computer system 500 may further include a video display unit 510 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 500 also includes an alphanumeric input device 512 (e.g., a keyboard), a user interface (UI) navigation or cursor control device 514 (e.g., a mouse), a disk drive unit 516, a signal generation device 518 (e.g., a speaker) and a network interface device 520.

Machine-Readable Medium

The disk drive unit 516 includes a machine-readable medium 522 on which is stored one or more set of data structures and instructions 524 (e.g., software) embodying or utilized by any one or more of the methodologies or functions described herein. The instructions 524 may also reside, completely or at least partially, within the main memory 504 and/or within the processor 502 during execution thereof by the computer system 500, with the main memory 504 and the processor 502 also constituting machine-readable media.

While the machine-readable medium 522 is shown in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more data structures or instructions 524. The term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the embodiments of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories and optical and magnetic media. Specific examples of machine-readable media include non-volatile memory, including, by way of example, semiconductor memory devices (e.g., Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices); magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Transmission Medium

The instructions 524 may further be transmitted or received over a communications network 526 using a transmission medium. The instructions 524 may be transmitted using the network interface device 520 and any one of a number of well-known transfer protocols (e.g., Hypertext Transfer Protocol “HTTP”). Examples of communication networks include a LAN, a WAN, the Internet, mobile telephone networks, plain old telephone (POTS) networks, and wireless data networks (e.g., WiFi and WiMax networks). The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such software.

Non-Limiting Embodiments

Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

Note on the Abstract

The Abstract of the Disclosure is provided to comply with 37 C.F.R.§1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 

1. A method comprising: tracking one or more patent annuity payments due on at least one patent for a user; docketing a due date for at least one of the annuity payments; in advance of the due date, identifying a cost of a forward contract to obtain or purchase currency equal to a total amount payable of the at least one annuity payment; and providing the cost of the forward contract to the user.
 2. The method of claim 1, further comprising receiving, in response to providing the cost of the forward contract, annuity payment instructions from the user.
 3. The method of claim 2 further comprising paying, or arranging to have paid, at least one annuity payment based on the received instructions.
 4. The method of claim 1, wherein the at least one annuity payment is due on a foreign patent and the currency is a foreign currency.
 5. The method of claim 1, wherein the due date of the at least one annuity payment falls within a specified period, and the cost identification occurs on a date in advance of the specified period.
 6. The method of claim 5, further comprising receiving data identifying one or both of the specified period and the cost identification date from the user.
 7. The method of claim 1, further comprising apportioning at least one component of the cost of the forward contract across a plurality of tracked annuity payments.
 8. The method of claim 7, wherein the at least one component is one or more of an interest charge, a currency conversion charge, and a bank or service charge relating to at least one aspect of the forward contract.
 9. The method of claim 7, wherein the apportionment is performed pro-rata based on a base cost of each annuity payment in the plurality of annuity payments.
 10. The method of claim 1, wherein the method is computer-implemented and wherein one or more of the tracking, docketing, identifying and providing is performed by at least one processor.
 11. A method of providing a patent annuity payment service, the method comprising: allowing a user to register with the service and to identify at least one patent on which an annuity is payable; generating, synchronizing or receiving annuity tracking data relating to the at least one patent, the tracking data including a due date of an annuity payment; identifying, in a first currency, an amount payable on the annuity payment; pricing, in advance of the due date and using forward contract rates from a participating bank, a forward contract for obtaining currency to have the annuity payment paid in a second currency; and providing the contract pricing to the user or a third party. 12-20. (canceled)
 21. An annuity payment management system comprising at least one hardware-implemented module including at least one processor to: track one or more patent annuity payments due on at least one patent for a user; docket a due date for at least one of the annuity payments; in advance of the due date, identify a cost of a forward contract to obtain or purchase currency equal to a total amount payable on the at least one annuity payment; and provide the cost of the forward contract to the user. 22-27. (canceled)
 30. An annuity payment management system, the system comprising at least one hardware-implemented module including at least one processor to: allow a user to register with the system and to identify at least one patent on which an annuity is payable; generate, synchronize or receive annuity tracking data relating to the at least one patent, the tracking data including a due date of an annuity payment; identify, in a first currency, an amount payable on the annuity payment; price, in advance of the due date and using forward contract rates from a participating bank, a forward contract for obtaining currency to have the annuity payment paid in a second currency; and provide the contract pricing to the user or a third party. 31-39. (canceled)
 40. An annuity payment management system comprising: a network; at least one database, accessible on the network, the database including data relating to annuity payments due on patents or applications registered at a patent office; a server, operatively connected to the network, wherein the server includes: a processor, a memory, software operable on the processor to: track one or more patent annuity payments due on at least one patent in the database; docket a due date for at least one of the annuity payments; in advance of the due date, identify a cost of a forward contract to obtain or purchase currency equal to a total amount payable on the at least one annuity payment; and provide the cost of the forward contract to a user.
 41. An annuity payment management system comprising: a network; at least one database, accessible on the network, the database including data relating to annuity payments due on patents or applications registered at a patent office; a server, operatively connected to the network, wherein the server includes: a processor, a memory, software operable on the processor to: allow a user to register with the system and to identify at least one patent on which an annuity is payable; generate, synchronize or receive annuity tracking data relating to the at least one patent, the tracking data including a due date of an annuity payment; identify, in a first currency, an amount payable on the annuity payment; price, in advance of the due date and using forward contract rates from a participating bank, a forward contract for obtaining currency to have the annuity payment paid in a second currency; and provide the contract pricing to the user or a third party. 